Authenticated device used to unlock another device

ABSTRACT

An electronic device that has a user-interface locked state and a user-interface unlocked state communicates with an external device using wireless communication to facilitate unlocking of the electronic device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/422,736, filed May 24, 2019, which is a continuation of U.S. patentapplication Ser. No. 14/719,217, filed May 21, 2015, which claims thebenefit of priority of U.S. Provisional Patent Application Ser. No.62/038,077, titled “AUTHENTICATED DEVICE USED TO UNLOCK ANOTHER DEVICE,”filed Aug. 15, 2014; U.S. Provisional Patent Application Ser. No.62/129,747, titled “AUTHENTICATED DEVICE USED TO UNLOCK ANOTHER DEVICE,”filed Mar. 6, 2015; and is a continuation of International ApplicationPCT/US15/25188, titled “AUTHENTICATED DEVICE USED TO UNLOCK ANOTHERDEVICE,” filed Apr. 9, 2015. The content of these applications is herebyincorporated by reference in its entirety.

This application relates to U.S. Patent Application Ser. No. 62/035,348,titled “CONTINUITY,” filed Aug. 8, 2014; and U.S. Patent ApplicationSer. No. 62/006,043, titled “CONTINUITY,” filed May 30, 2014. Thecontent of these applications is hereby incorporated by reference in itsentirety.

BACKGROUND 1. Field

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for permitting a user to transitionfrom use of one device to another, seamlessly.

2. Description of Related Art

Modern electronic devices may have multiple input mechanisms such astouchscreens, touchpads, and/or buttons. One problem associated withusing these input mechanisms is the unintentional activation ordeactivation of functions due to unintentional contact. To address thisproblem, some devices may be locked upon satisfaction of predefined lockconditions, such as after a predetermined time of idleness has elapsed,or upon manual locking by a user. When locked, a device may remainoperational but ignore most, if not all, user input so as to reduce thelikelihood of unintentional action. That is, the device, its inputmechanisms, and/or applications running thereon may ignore certainclasses of input when locked.

One class of input that a locked device may still respond to is attemptsto unlock the device. These inputs may involve known unlockingprocedures, such as pressing a predefined set of buttons (simultaneouslyor sequentially) or entering a code or password. These unlock procedureshave drawbacks, however. The button combinations may be hard to perform.Creating, memorizing, and recalling passwords, codes, and the like canbe burdensome. These drawbacks are further exacerbated when a userswitches between uses of multiple devices that require unlocking,particularly when the devices are configured to auto-lock after someduration of idleness.

There is a need for more efficient, user-friendly procedures forunlocking such devices, input mechanisms, and/or applications.

BRIEF SUMMARY

In some embodiments, a method of unlocking an electronic device using anauthenticated, external device comprises: at the electronic device,where the electronic device has a user-interface locked state and auser-interface unlocked state: detecting, via wireless communication, anexternal device; receiving, from the external device, unlockinginformation for unlocking the electronic device; detecting, while in thelocked state, user input; and in response to detecting the user inputand the received unlocking information, unlocking the electronic device.

In some embodiments, a method of using an electronic device (that hasbeen authenticated) to unlock an external device comprises: at anelectronic device, where the electronic device has a user-interfacelocked state and a user-interface unlock state, and is in theuser-interface unlocked state: detecting, via wireless communication, anexternal device, where the external device has a user-interface lockedstate and a user-interface unlocked state, and is in the user-interfacelocked state; and transmitting, to the external device, unlocking data,where the external device unlocks after the external device receives theunlocking information and detects user input.

In some embodiments, a method of configuring an electronic device torecognize that an external device is an authenticated external devicethat may be used to facilitate the (automatic) unlock of the electronicdevice comprises: at the electronic device, where the electronic devicehas a user-interface locked state and a user-interface unlocked state,the electronic device within wireless communication range of an externaldevice: receiving at the electronic device, while in the user-interfacelocked state, user input representing a credential for unlocking theelectronic device. In response to a determination that the credential isvalid, unlocking the electronic device. After unlocking, displaying, ona screen of the electronic device, an identification of the externaldevice; and prompting a user to designate whether the external device isauthorized to unlock the electronic device if, in the future, theexternal device comes within wireless communication range of theelectronic device while the electronic device is in the user-interfacelocked state.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having atouch-sensitive display in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIG. 6A illustrates exemplary devices for performing auto-unlocktechniques.

FIG. 6B illustrates exemplary devices for performing auto-unlocktechniques.

FIG. 6C illustrates exemplary devices for performing auto-unlocktechniques.

FIG. 6D illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 6E illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 6F illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 7A illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 7B illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 7C illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 7D illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 7E illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 7F illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 8A illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 8B illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 8C illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 9A illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 9B illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 10A illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 10B illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 10C illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 10D illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 11A illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 11B illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 11C illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 11D illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 11E illustrates exemplary user interface(s) for unlocking anelectronic device.

FIG. 12 is a flow diagram illustrating a process for unlocking anelectronic device.

FIG. 13 is a flow diagram illustrating a process for unlocking anelectronic device.

FIG. 14 is a flow diagram illustrating a process for unlocking anelectronic device.

FIG. 15 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 16 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 17 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 18 is a functional block diagram of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

It is desirable for a device that is trusted by other electronic devices(e.g., an “authenticated” device) to able to facilitate the unlocking ofcertain other electronic devices. Consider the situation in which a userowns and switches between uses of multiple electronic devicesfrequently. Upon unlocking one electronic device (e.g., by providing apassword), would be useful for nearby devices (that are within wirelesscommunications range) to also unlock automatically, or at least requirea reduced set of user input for unlocking. In this way, the user maytransition between different devices quickly, without having to entercorresponding passwords on each device. Techniques for performing thesefunctionalities—using an authenticated device to unlock other electronicdevices—may be referred to as auto-unlocking techniques.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices that may perform auto-unlocking techniques. FIGS. 6-11illustrate exemplary user interfaces involved in the auto-unlocking ofdevices. The user interfaces in the figures are also used to illustratethe auto-unlocking processes described below, including the processes inFIGS. 12-14.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and is sometimesknown as or called a touch-sensitive display system. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on the touchsensitive surface, or to a substitute (proxy) for the force or pressureof a contact on the touch sensitive surface. The intensity of a contacthas a range of values that includes at least four distinct values andmore typically includes hundreds of distinct values (e.g., at least256). Intensity of a contact is, optionally, determined (or measured)using various approaches and various sensors or combinations of sensors.For example, one or more force sensors underneath or adjacent to thetouch-sensitive surface are, optionally, used to measure force atvarious points on the touch-sensitive surface. In some implementations,force measurements from multiple force sensors are combined (e.g., aweighted average) to determine an estimated force of a contact.Similarly, a pressure-sensitive tip of a stylus is, optionally, used todetermine a pressure of the stylus on the touch-sensitive surface.Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure and the estimated force or pressure isused to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/or applicationspecific integrated circuits.

Memory 102 may include one or more computer readable storage mediums.The computer readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 801.11nand/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161 and one or more input controllers 160 forother input or control devices. The one or more input controllers 160receive/send electrical signals from/to other input or control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, infrared port, USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 and convertthe detected contact into interaction with user-interface objects (e.g.,one or more soft keys, icons, web-pages or images) that are displayed ontouch screen 112. In an exemplary embodiment, a point of contact betweentouch screen 112 and the user corresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Patents: U.S. Pat. No. 6,323,846 (Westerman et al.), U.S.Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereas touchsensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device, so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112 which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112 which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and other touchsensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementationsa user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast or other visual property) of graphicsthat are displayed. As used herein, the term “graphics” includes anyobject that can be displayed to a user, including without limitationtext, web pages, icons (such as user-interface objects including softkeys), digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video Conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contacts module 137, and telephone module138, video conference module 139 includes executable instructions toinitiate, conduct, and terminate a video conference between a user andone or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web-pages or portionsthereof, as well as attachments and other files linked to web-pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web-page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions; data on stores and otherpoints of interest at or near a particular location; and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177 or GUI updater 178 to update the application internalstate 192. Alternatively, one or more of the application views 191include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of the aboveidentified modules corresponds to a set of instructions for performing afunction described above. The above identified modules or programs(e.g., sets of instructions) need not be implemented as separatesoftware programs, procedures or modules, and thus various subsets ofthese modules may be combined or otherwise rearranged in variousembodiments. In some embodiments, memory 370 may store a subset of themodules and data structures identified above. Furthermore, memory 370may store additional modules and data structures not described above.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online Video”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 are labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments the touch sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 500can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 500.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013 and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 may be a rotatable input device or a depressible androtatable input device, for example. Input mechanism 508 may be abutton, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personalelectronic device 500 can include various sensors, such as GPS sensor532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 1200-1500 (FIGS. 12-15).The computer-executable instructions can also be stored and/ortransported within any non-transitory computer readable storage mediumfor use by or in connection with an instruction execution system,apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. For purposes of this document, a“non-transitory computer readable storage medium” can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. The non-transitory computer readable storage medium can include,but is not limited to, magnetic, optical, and/or semiconductor storages.Examples of such storage include magnetic disks, optical discs based onCD, DVD, or Blu-ray technologies, as well as persistent solid-statememory such as flash, solid-state drives, and the like. Personalelectronic device 500 is not limited to the components and configurationof FIG. 5B, but can include other or additional components in multipleconfigurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of device 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example,an image (e.g., icon), a button, and text (e.g., hyperlink) may eachconstitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In, some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments the contact-detection intensity threshold is zero.In some embodiments the contact-detection intensity threshold is greaterthan zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the term “open application” or “executing application”refers to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application may be any one of thefollowing types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes) which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed to towards user interfaces (“UP”) andassociated processes that may be implemented on a multifunction devicewith a display and a touch-sensitive surface, such as devices 100, 300,and/or 500 (FIGS. 1A, 3A, and/or 5A), to provide auto-unlockingfunctionalities.

1. User-Interface Lock and Unlock States

FIG. 6A illustrates exemplary electronic devices 600, 602, and 604.Device 600 may be device 100 (FIG. 1A) in some embodiments. In theillustrated example, device 600 is a phone. Device 602 may be device 300(FIG. 3A) in some embodiments. In the illustrated example, device 602 isa laptop. Device 604 may be device 500 (FIG. 5A) in some embodiments. Inthe illustrated example, device 604 is a wearable electronic device.

Devices 600, 602, and 604 may each have a user-interface lock state anda user-interface unlock state. In the user-interface lock state(hereinafter the “lock state”), a device such as device 600, 602, or 604is powered on and operational but ignores most, if not all, user input.That is, the device takes no action in response to user input and/or thedevice is prevented from performing a predefined set of operations inresponse to the user input. The predefined set of operations may includenavigation between user interfaces and activation or deactivation of apredefined set of functions. The lock state may be used to preventunintentional or unauthorized use of the device or activation ordeactivation of functions on the device. A device may enter the lockstate in response to user instruction to do so. A device may also enterthe lock state after a period of idleness. The period may be specifiedby the user as a configuration setting. When the device is in the lockstate, the device may be said to be locked. As shown, devices 600, 602,and 604 are locked.

In some embodiments, a device in the lock state may still respond to alimited set of user inputs, including input that corresponds to anattempt to transition the device to the user-interface unlock state orinput that corresponds to powering the device off. In other words, thelocked device responds to user input corresponding to attempts totransition the device to the user-interface unlock state or powering thedevice off, but does not respond to user input corresponding to attemptsto navigate between user interfaces. Also, even if the device ignores auser input, the device may still provide sensory feedback (such asvisual, audio, or vibration feedback) to the user upon detection of theinput to indicate that the input will be ignored.

In the user-interface unlock state (hereinafter the “unlock state”), thedevice is in its normal operating state, detecting and responding touser input corresponding to interaction with the user interface. Adevice that is in the unlock state may be said to be unlocked. Anunlocked device detects and responds to user input for navigatingbetween user interfaces, entry of data and activation or deactivation offunctions, and so forth. In embodiments where the device includes atouch-sensitive input mechanism, the unlocked device detects andresponds to contact corresponding to navigation between user interfaces,entry of data and activation or deactivation of functions through thetouch-sensitive input mechanism. In embodiments where the deviceincludes a rotatable input mechanism, the unlocked device detects andresponds to rotations and/or depressions corresponding to navigationbetween user interfaces, entry of data and activation or deactivation offunctions through the rotatable input mechanism.

FIG. 6B illustrates user 606 who uses multiple electronic devicesincluding devices 600, 602, and 604. Each of these devices may belocked. To use a particular device, user 606 may have to first unlockthe device. As discussed above, this process may become burdensome,particularly if the devices are configured to automatically lock aftersome period of idleness.

FIG. 6C illustrates an exemplary situation in which the use of anauthenticated device to unlock other electronic devices may bedesirable. As shown, user 606 is readying to use device 602, a laptop.Device 602 may be configured to power-up into a locked state. User 606,however, may have been interacting with devices 600 or 604, meaning thatdevices 600 and/or 604 may still be unlocked. Devices 600 and 604 arealso in physical proximity (e.g., within wireless communication range)of device 602. In this situation, it would be helpful for either device600 or 604 to provide device 602 with credentials, such that device 602may require minimal or no additional user input to unlock, therebypermitting user 606 to begin productive work on the device.

Attention is now directed to techniques for unlocking device 602 usingunlocked device(s) 600 and 604, with reference to FIGS. 6D-6F. FIG. 6Ddepicts device 602 displaying user interface lock screen 608 indicatingthat the device is locked. In this state, device 602 accepts passwordentries in password input field 610 to unlock the device. It would behelpful for user 606 to be able to gain access to device 602 withouthaving to manually enter a password, however. As shown in FIG. 6E,external device 604 may be within communications range of device 602.Device 602 may detect the presence of device 604 via a wirelesscommunication protocol. Low-powered wireless communications may beparticularly suited for this purpose. Examples of suitable wirelesscommunications include Bluetooth® and Bluetooth Low Energy (BTLE).Similarly, devices 604 may detect nearby device 602.

As shown, external device 604 is in its unlocked state (e.g., normaloperating mode), possibly due to recent usage by user 606 (FIG. 6C).Upon detection, device 604 may transmit, to device 602, information forfacilitating the unlocking of device 602, such as user credentials.Assuming that device 602 trusts device 604, device 602 may use thereceived credentials information to facilitate its unlocking process.

In some embodiments, device 602 may unlock upon receiving thecredentials information and, additionally, detecting a user input. Theuser input may be a mouse input such as a mouse movement or a mouseclick. The user input may be a touch input such as a tap or a swipe. Theuser input may be a depression of a mechanical or capacitive inputmechanism. In the illustrated example, upon receiving unlockinginformation from device 604, device 602 replaces password input field610 (FIG. 6D) with affordance 612, which when selected (e.g., clicked),unlocks device 602. Note that, in embodiments requiring the detection ofuser input before unlocking, mere placement of devices (e.g., 604 and602) into physical proximity, without more, should not be considered adetected user input.

In some embodiments, upon receiving credentials information from device604, device 602 may automatically unlock without requiring further userinput. In some embodiments, upon receiving credentials information fromdevice 604, device 602 may unlock after detecting a valid biometricreading from a biometric input device. In these embodiments, theadditional biometric reading may be used to form a two-factorauthentication process.

FIG. 6F illustrates device 602 in the unlocked state. In this state,device 602 may display desktop screen 614 having affordances forlaunching various application programs (e.g., icon 616 for launching amessaging application). Optionally, device 604 may display visualindicator 616 and/or haptic feedback indicating that device 604 haseffected the unlocking of device 602.

It is noted that although FIGS. 6D-6F illustrate the unlocking of device602 with external device 604, the described techniques may be extendedto cover other devices, such as devices 100, 300, 500. (FIGS. 1A, 3A,and 5A). That is to say, permutations of various electronic devicesacting as lock and key are possible. For example, in some embodiments,device 100 (FIG. 1A) may act as an authenticated device for unlockingdevice 500 (FIG. 5A), as discussed below with reference to FIGS. 7A-7E.For example, in some embodiments, device 500 (FIG. 5A) may act as anauthenticated device for unlocking device 100 (FIG. 1A), as discussedbelow with reference to FIGS. 8A-8C. For brevity, other permutations,while possible, are not explicitly discussed here.

Attention is now directed to additional techniques for using anauthenticated device to unlock another electronic device, with referenceto FIGS. 7A-7E. FIG. 7A depicts exemplary device 700, which may bedevice 500 (FIG. 5A) in some embodiments. Device 700 may have a displayscreen that turns off under some circumstances. For example, its displayscreen may turn off after a predetermined duration of idleness. Thedisplay screen of device 700 may turn on again in response to movementand/or user input. When the display screen of device 700 turns on, itmay display lock screen 702 indicating that device 700 is locked. Lockscreen 702 may prompt the user for a password for unlocking the device.

FIG. 7B depicts the presence of external device 704 within wirelesscommunications range of device 700. Device 704 may be device 100 (FIG.1A) in some embodiments. External device 704 may also be in the lockedstate, as shown by lock screen 706. Lock screen 706 may have instruction708 indicating how device 704 may be unlocked. As device 704 is itselflocked, device 700 does not respond by automatically unlocking.

FIG. 7C depicts user input 710 representing a user's attempt to unlockdevice 704. As shown, device 700 remains in its locked state whileattempts are made to unlock device 704. FIG. 7D depicts further userinput 712 representing the user's continued attempt to unlock device704. Device 700 continues to remain in its locked state.

Turning to FIG. 7E, upon receiving a valid passcode via user input 712(FIG. 7D), device 704 unlocks into its normal operating state. As shown,device 704 is executing active application 714. Application 714 may be amessaging application, such as Messages by Apple Inc. of Cupertino,Calif. After unlocking, device 704 also may transmit information todevice 700, including information that facilitates the automaticunlocking of device 700.

In the example illustrated in FIG. 7F, upon receiving this information,device 700 automatically unlocks without requiring further user input,and displays clock screen 716. In some embodiments, device 700 mayunlock upon receiving the credentials information and detecting a userinput. The user input may be a movement of device 700. The user inputmay be a touch input such as a tap or a swipe. The user input may be adepression of a mechanical or capacitive input mechanism.

Attention is now directed to additional techniques for using anauthenticated device to unlocking another electronic device, withreference to FIGS. 8A-8C. FIG. 8A depicts exemplary device 800, whichmay be device 100 (FIG. 1A) in some embodiments. Device 800 may have adisplay screen that turns off under some circumstances. For example, itsdisplay screen may turn off after a period of idleness. The displayscreen of device 800 may turn on again in response to movement of and/oruser input. When the display screen of device 800 turns on, it maydisplay lock screen 802 indicating that device 800 is locked. Lockscreen 802 may have instruction 804 indicating how to unlock device 800.

FIG. 8B depicts the presence of external device 806 within wirelesscommunications range of device 800. Device 806 may be device 500 (FIG.5A) in some embodiments. Device 806 may have been recently used by theuser (e.g., within the last 5-20 seconds), and therefore may beunlocked. Device 806 may transmit information to device 800 thatfacilitates the automatic unlocking of device 800. As shown in FIG. 8C,upon receiving this information, device 800 may automatically unlockwithout requiring further user input, thereby replacing lock screen 802(FIG. 8B) with menu 808 having various application icons. In someembodiments, device 800 may require some user input (e.g., asubstantially horizontal swipe) before unlocking.

2. Continuity of Application States Across Devices

As a user switches between uses of different devices, in addition tohaving devices auto-unlock, it would be helpful for the user to be ableto transition content that is being displayed on one device ontoanother. Co-pending U.S. Provisional Application No. 62/035,348, titled“CONTINUITY,” filed Aug. 8, 2014, and incorporated herein in itsentirety, describes the continuity of applications across multipleelectronic devices, in that a user may work in one application on onedevice, and transition the work onto a nearby device that is withinwireless communication range.

Aspects of continuity may be incorporated into the above-described userinterfaces for using an authenticated device to unlock other devices.For example, as a target device auto-unlocks, it may be desirable forthe target device to also launch the same application that is executingon the authenticated external device. It also may be desirable for theapplication, upon launching, to have the same application state (e.g.,display the same information that is displayed on the authenticatedexternal device).

These features are described with reference to FIGS. 9A-9B. As shown inFIG. 9A, device 900 (which may be device 100 of FIG. 1A in someembodiments) and device 902 (which may be device 500 of FIG. 5A in someembodiments) are within wireless communications range. As shown, device900 is locked and device 902 is unlocked. Device 902 may be displayingmessage transcript 906 via an active messaging application. Device 902may transmit information to device 900 to facilitate the unlocking ofdevice 900. In addition to user credentials, the information may includean identification of the application that is active on device 902 (e.g.,the messaging application) and/or application state information (e.g.,message transcript 906).

Device 900 may be configured to require a password before unlocking.However, having received unlocking information from device 902, device900 may unlock without requiring the entry of additional passwordinformation. The additionally received application and/or applicationstate information permits device 900 to further provide continuityfunctions after unlocking.

In the illustrated embodiment, in response to the transmittedinformation, device 900 may display affordance 904 indicating that acorresponding (messaging) application will be launched upon unlockingdevice 900. Also, affordance 904 may have a visual indicationidentifying the application (e.g., messaging) that will be launched whendevice 900 unlocks. As depicted in FIG. 9B, upon unlocking, device 900may launch corresponding messaging application and display the samemessage transcript 906 being displayed on device 902. The amount ofmessage transcript 906 displayed on devices 900 and 902 may varydepending on the form factors (e.g., display screen size and resolution)of the devices

In some embodiments (not illustrated), in place of affordance 904,device 900 may display an instruction on lock screen 908 indicating thatthe messaging application will be launched if the user proceeds tounlock device 900. For example, device 900 may display the instruction:“Slide to open Messages”. In some embodiments (not illustrated),responsive to the transmitted information, device 900 may permitunlocking via a single push of its mechanical input mechanism 910, andlaunch the corresponding application (e.g., Messages) upon unlocking. Insome embodiments (not illustrated), responsive to the informationtransmitted from device 902, device 900 may simply unlock and launch thecorresponding application without requiring further user input.

In some embodiments, device 900 may permit a user to unlock the devicewithout necessarily invoking continuity functionality. Whether device900 invokes continuity functionality may depend on the user input usedto unlock device 900. For example, device 900 may launch a correspondingapplication if the user taps affordance 904, and yet refrain fromlaunching the application if the user taps mechanical input mechanism910 to unlock. Instead, when the user taps button 910, device 900 mayunlock to display the most recently used application on device 900.

3. Authenticated Devices

Although it is useful for electronic devices to unlock one another invarious situations, for privacy reasons, caution may be required incontrolling which electronic devices are able to be able to facilitatethe auto-unlocking of other devices. To put another way, it may benecessary to determine which electronic devices are to be authenticatedfor purposes of auto-unlocking functionality. Attention is now directedto user interfaces for authenticating devices for purposes ofauto-unlocking devices such as devices 100, 300, and 500 (FIGS. 1A, 3A,and 5A).

In some embodiments, a device may prompt the user as to whether a nearbyexternal device should become authenticated, meaning whether theexternal device should become able to unlock the (prompting) device.This aspect is described with reference to FIGS. 10A-10D. FIG. 10Adepicts device 1000, which may be device 300 (FIG. 3A) in someembodiments. Device 1000 may display lock screen 1002 indicating that itis locked. Lock screen 1002 may include password input field 1004 forunlocking device 1000.

FIG. 10B depicts the presence of external device 1010 within wirelesscommunication range of device 1000. External device 1010 may be any oneof devices 100, 300, or 500 (FIGS. 1A, 3A, 5A). In the illustratedembodiment, external device 1010 is device 500 (FIG. 5A). Externaldevice 1010 is shown in the unlocked state, actively executing amessaging application to display message transcript 1012. Device 1000and external device 1010 may detect one another over wirelesscommunication. External device 1010 may transmit information to device1000 for facilitating the unlocking of device 1000.

In some embodiments, device 1000 may decline to unlock automaticallybased on the received information, because it has not been configured totrust device 1010. Restated, from the perspective of device 1000, device1010 is not an authenticated device. As such, device 1000 may continueto display lock screen 1002. However, a user may manually unlock device1000 while external device 1010 is still in-range. For example, the usermay enter a valid password into password input field 1004 to unlockdevice 1002, as shown in FIG. 10B.

Turning to FIG. 10C, when the user manually unlocks device 1000 in thepresence of unlocked external device 1010, device 1000 may prompt theuser to indicate whether device 1000 should become an authenticateddevice. That is, device 1000 may ask whether external device 1010 shouldbe permitted to auto-unlock device 1000, in the future, when externaldevice 1010 comes into communications range again. The prompt mayinclude an identification of external device 1010 by its make/modeland/or its device name.

If the user responds in the affirmative (e.g., by selecting affordance1012), device 1000 may register external device 1010 as an authenticateddevice, meaning that external device 1010 becomes an authenticateddevice for purposes of auto-unlocking device 1000. Restated, device 1010is authorized to unlock device 1000 if, in the future, external device1010 comes within wireless communication range of device 1000, andexternal device 1010 is unlocked while device 1000 is locked.

Additionally, in some embodiments, device 1000 may prompt the user toconfirm the authentication of device 1002 by re-entering the user'spassword (for unlocking device 1000) on device 1000, as shown in FIG.10D. In this way, device 1002 becomes able to auto-unlock device 1000 inthe future.

If the user responds in the negative (e.g., by selecting affordance1014), device 1000 may remember external device 1010 as anon-authenticated device. Accordingly, device 1000 may refrain fromautomatically prompting the user about authenticating external device1010, should the two devices come into wireless communication again inthe future. Device 1000 may also refrain from automatically unlockingwhen device 1010 comes within wireless communication range again in thefuture.

In some embodiments, a device may provide access to configurationsettings that control whether certain external devices should beauthenticated for purposes of auto-unlock features. This aspect isdescribed with reference to FIGS. 11A-11C. FIG. 11A depicts device 1100,which may be device 300 (FIG. 3A) in some embodiments. Device 1100 maybe unlocked and displaying desktop screen 1102. Desktop screen 1102 mayhave graphical user interface affordances for launching applications andother features, such as icon 1104 for configuring device settings.Configurable settings may include settings that identify externalelectronic devices for facilitating automatic unlocking of device 1100.

As shown in FIG. 11B, device 1100 may display listing 1106 of externaldevices that may become authenticated devices for purposes ofauto-unlocking device 1100. The devices appearing in listing 1106 may bedetermined through various techniques. In some embodiments, device 1100may be associated with a user identifier (e.g., an account or an e-mailaddress), and device 1100 may populate listing 1106 to include otherdevices associated with the same user account. In some embodiments,device 1100 may be a trusted member of a security domain, and device 110may populate listing 1106 with external devices are trusted members ofthe same security domain. In some embodiments, device 1100 may contact asecurity or authentication server to determine whether two electronicdevices are associated with one another. For example, device 1100 maycontact a server to retrieve a list of devices that are trusted to aparticular domain and/or registered to a given user identifier. In someembodiments, device 1100 may populate listing 1106 based on the physicalproximity of external devices. For example, listing 1106 may list onlythose devices that are currently within wireless communication distancevia a low-powered wireless communication protocol.

Listing 1106 may have checkboxes next to external devices that arelisted. The checkboxes may specify whether the corresponding externaldevices should become authenticated for purposes of facilitating theauto-unlocking of device 1100. In the illustrated example, device 1100displays listing 1106 with checkboxes 1108 and 1110 corresponding a“phone” and a “tablet” device. The “phone” and “tablet” devices, anddevice 1100, may each be associated with the same user identifier on acloud-based service, such as iCloud® by Apple Inc. of Cupertino, Calif.

FIG. 11C illustrates a possible response, of device 1100, to a user'sselection of checkbox 1110. In the illustrated example, device 1100requires a particular external device to be within communications rangeof device 1110 at the time of authentication for purposes ofauto-unlocking functionality. In the illustrated example, the user'stablet computer lies outside of communications range with device 1100.Device 1110 thus displays message 1112 indicating that the tablet cannotbe authenticated for purposes of auto-unlocking functionality.

FIGS. 11D-11E illustrates a possible response, by device 1100, to auser's selection of checkbox 1108. Checkbox 1108 represents the user'sphone 1114, which is within communications range of device 1100 in theillustrated example. In this instance, device 1100 may register phone1114 as an authenticated device, meaning that phone 1114 becomesauthorized to unlock device 1100 if, in the future, phone 1114 appearswithin wireless communication range of device 1100, and phone 1114 isunlocked. Turning to FIG. 11E, device 1100 may further require the userto confirm the authentication of phone 1114 by entering the password forunlocking device 1100, on device 1100.

FIG. 12 is a flow diagram illustrating process 1200 for unlocking anelectronic device using an authenticated external device. Process 1200may be carried out by electronic devices such as devices 100, 300,and/or 500 (FIGS. 1A, 3A, 5A) in various embodiments. At block 1202, theelectronic device, which is locked, detects an external device viawireless communication. The electronic device may verify that thedetected external device is authenticated for purposes of auto-unlockingfunctionality. At block 1204, the electronic device receives, from theexternal device, unlocking information for unlocking the electronicdevice. The electronic device may confirm that the received informationis valid and authentic. At block 1206, the electronic device detects,while in the locked state, user input. At block 1208, responsive to thereceived information and the detected user input, the device may unlockinto its normal operating state. For example, in the unlocked state, theelectronic device may permit a user to launch an application.Optionally, at block 1210, the electronic device may launch anapplication upon unlocking. The application that is launched may be thesame application that is active on the external device. Optionally, whenlaunched, the application may enter the same application state as theapplication that is active on the external device. That is, for example,the newly launched application, on the electronic device, may obtain anddisplay the same web page or e-mail that is being displayed on theexternal device.

FIG. 13 is a flow diagram illustrating process 1300 for using anelectronic device to unlock an external electronic device. Process 1300may be carried out by electronic devices such as devices 100, 300,and/or 500 (FIGS. 1A, 3A, 5A) in various embodiments. The electronicdevice, which has a user-interface locked state and a user-interfaceunlock state, may be in the user-interface unlocked state. At block1302, the electronic device may detect, via wireless communication, theexternal device. The external device also has a user-interface lockedstate and a user-interface unlocked state, and is in the user-interfacelocked state. At block 1304, the electronic device may transmit, to theexternal device, unlocking data, thereby causing the external device tounlock after the external device receives the unlocking information anddetects user input. Optionally, at block 1306, the electronic device mayprovide a visual confirmation and/or a haptic confirmation that theexternal device has been unlocked. The confirmation may be providedafter the electronic device obtains a confirmation that the externaldevice has been unlocked.

FIG. 14 is a flow diagram illustrating process 1400 for configuring anelectronic device to recognize an external device as an authenticatedexternal device for purposes of auto-unlocking functionality. Process1400 may be carried out by electronic devices such as devices 100, 300,and/or 500 (FIGS. 1A, 3A, 5A) in various embodiments. At block 1402, theelectronic device, which has a user-interface locked state and auser-interface unlocked state, may detect within its wirelesscommunication range an external device. At block 1404, the electronicdevice may determine whether the external device has been previouslyauthenticated for purposes of auto-unlocking the electronic device.

If the external device is an authenticated device for purposes ofauto-unlocking the electronic device, the electronic device may proceedto auto-unlock, through the above-discussed user interfaces illustratedin FIGS. 5-7 and through process 1200 (FIG. 12), for example. If theexternal device has been previously registered as a non-authenticateddevice for purposes of auto-unlock functionality, the electronic devicemay remain locked and await other potential attempts at unlocking (suchas the manual entry of a password).

If the external device has not yet been registered as eitherauthenticated or non-authenticated, processing may proceed to block1406, where the electronic device (which is locked), may receive userinput representing a credential for unlocking the electronic device. Inaddition, the electronic device may verify the received credentials andunlock as appropriate. At block 1408, after unlocking, the electronicdevice may display an identification of the external device indicatingthat the two devices are physically proximate (e.g., within wirelesscommunication range of a low powered communication protocol) and thatthe external device may become authenticated for purposes ofauto-unlocking functionality. At block 1410, the electronic device mayprompt the user to designate whether the external device should becomeauthorized to unlock the electronic device if, in the future, theexternal device comes within wireless communication range of theelectronic device while the electronic device is in the user-interfacelocked state.

FIG. 15 shows exemplary functional blocks of an electronic device 1500that, in some embodiments, performs the above-described features. Asshown in FIG. 15, an electronic device 1500 may include display unit1502 configured to display graphical objects; human input interface unit1504 configured to receive user input; one or more RF units 1506configured to detect and communicate with external electronic devices;one or more feedback unit configured to provide user with haptic, audio,and/or visual feedback; and processing unit 1510 coupled to display unit1502, human input interface unit 1504, RF unit(s) 1506, and feedbackunit 1508. In some embodiments, processing unit 1510 is configured tosupport an operating system running on operating system unit 1512. Inturn, operating system unit 1512 may support an applications unit 1514for launching and running one or more applications.

In some embodiments, the processing unit 1510 includes a displayenabling unit 1516 and a security unit 1518. In some embodiments, thedisplay enabling unit 1516 is configured to cause a display of a userinterface (or portions of a user interface) in conjunction with thedisplay unit 1502. For example, the display enabling unit 1516 may beused for: displaying a lock screen, displaying an unlocked screen,displaying a menu of application icons; displaying a desktop screen;displaying a prompt that prompts the user to specify whether an externaldevice should become authenticated for purposes of auto-unlockingfeatures.

In some embodiments, RF unit 1506 is configured to detect and receiveinformation from an external device, such as credential information forfacilitate the unlocking of the receiving device, applicationinformation, application state information, so forth. In someembodiments, the RF unit is configured to detect and transmitinformation to an external device, such as credential information forfacilitating the unlocking of the receiving device, applicationinformation, application state information, so forth.

In some embodiments, the security unit 1518 is configured to receiveinput, e.g., through the use of human input interface unit 1504 and/orRF unit 1506. For example, security unit 1518 may determine whetherinformation received from RF unit 1506 represents an authenticateddevice that can be used to facilitate unlocking. Security unit 1518 mayalso determine whether information received from human input interfaceunit 1504 is a set of valid credentials for unlocking electronic device1500. Security unit 1518 may determine whether to unlock device 1500based on received information from human input interface unit 1504and/or RF unit 1506. Security unit 1518 may also cause the other unitsof device 1500 to prompt the user as to whether an external deviceshould become authenticated for purposes of auto-unlockingfunctionality. Security unit 1518 may register authenticated devices sothat device 1500 may recognize authenticated devices.

The units of FIG. 15 may be used to implement the various techniques andmethods described above with respect to FIGS. 6-14. The units of device1500 are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described examples. It is understood by persons of skill in theart that the functional blocks described in FIG. 15 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described examples. Therefore, the description herein optionallysupports any possible combination or separation or further definition ofthe functional blocks described herein.

In accordance with some embodiments, FIG. 16 shows a functional blockdiagram of an electronic device 1600 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 16 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 16, an electronic device 1600 includes a display unit1602 configured to display a graphic user interface, optionally, a touchsensitive surface unit 1604 configured to receive contacts, and aprocessing unit 1606 coupled to the display unit 1602 and, optionally,the touch-sensitive surface unit 1604. In some embodiments, theprocessing unit 1606 includes a detecting unit 1608, a receiving unit1610, an unlocking unit 1612, an obtaining unit 1614, a display enablingunit 1616, a prompt enabling unit 1618, a launching unit 1620, aninvoking unit 1622, and a transmitting unit 1624. The electronic device1600, optionally, has a user-interface locked state and a user-interfaceunlocked state.

The processing unit 1606 is configured to detect (e.g., with thedetecting unit 1608), via wireless communication, an external device;receive (e.g., with the receiving unit 1610), from the external device,unlocking information for unlocking the electronic device; detect (e.g.,with the detecting unit 1608), while in the locked state, user input;and in response to detecting the user input and the received unlockinginformation, unlock (e.g., with the unlocking unit 1612) the electronicdevice.

In some embodiments, the external device has a user-interface lockedstate and a user-interface unlock state, the processing unit 1606further configured to obtain (e.g., with the obtaining unit 1614) anindication that the external device is in the user-interface unlockedstate, and unlock (e.g., with the unlocking unit 1612) the electronicdevice in response to the received unlocking information and thereceived user input, if the external device is in the user-interfaceunlocked state.

In some embodiments, the processing unit 1606 is further configured toenable display (e.g., with the display enabling unit 1616) of a visualindication on the electronic device indicating that it is in theuser-interface unlocked state, after unlocking the electronic device.

In some embodiments, the external device displays a visual indicationindicating that the electronic device is in the user-interface unlockedstate, after the electronic device unlocks

In some embodiments, the external device causes a haptic eventindicating that the electronic device is in the user-interface unlockedstate, after the electronic device unlocks.

In some embodiments, the processing unit 1606 is further configured toreceive (e.g., with the receiving unit 1610), while in theuser-interface locked state, input data representing user input of apassword; and in response to receiving the input data: enable prompting(e.g., with the prompt enabling unit 1618) of, on a display of theelectronic device, a user to designate whether the external device isauthorized to unlock the electronic device.

In some embodiments, the input data comprising a reading from abiometric sensor of the electronic device and/or a biometric sensor ofthe external device.

In some embodiments, the input data comprising a touch on atouch-sensitive input of the electronic device.

In some embodiments, the input data comprising movement of a mousecoupled to the electronic device and/or a mouse coupled to the externaldevice.

In some embodiments, the user input comprising a keystroke on a keyboardof the electronic device.

In some embodiments, the processing unit 1606 is further configured toreceive, from the external device, usage information indicating usage ofthe first application on the external device; and after unlocking,launch a second application on the electronic device, the secondapplication corresponding to the first application.

In some embodiments, launching the second application comprises invokingthe state in the second application on the electronic device.

In some embodiments, the detected user input is a user input on theelectronic device.

In some embodiments, the unlocking information includes identificationdata based on an e-mail address associated with the electronic device,the processing unit 1606 further configured to unlock (e.g., with theunlocking unit 1612) the electronic device in response to the receivedunlocking information and the received user input, if the externaldevice is associated with the e-mail address associated with theelectronic device.

In some embodiments, the unlocking information includes identificationdata identifying the external device, the processing unit 1606 furtherconfigured to transmit (e.g., with the transmitting unit 1624), to anauthentication server, at least a portion of the identification data;receive (e.g., with the receiving unit 1610), from the authenticationserver, an indication of whether the external device is authorized tounlock the electronic device; and unlock (e.g., with the unlocking unit1612) the electronic device in response to the received unlockinginformation and the received user input, if the external device isauthorized.

In some embodiments, the unlocking information includes identificationof a security domain associated with the external device, the processingunit 1606 further configured to unlock (e.g., with the unlocking unit1612) the electronic device in response to the received unlockinginformation and the received user input, if the electronic device isassociated with the same security domain.

In some embodiments, the processing unit 1606 is further configured todetect (e.g., with the detecting unit 1608), via a peer-to-peer wirelesscommunication, the external device.

In some embodiments, the wireless communication comprises Bluetoothcommunication.

In some embodiments, the external device is a wearable electronicdevice.

The operations described above with reference to FIG. 12 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.16. For example, detecting operations 1202 and 1206, receiving operation1204, and unlocking operations 1208 and 1210 are, optionally,implemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 17 shows a functional blockdiagram of an electronic device 1700 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 17 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 17, an electronic device 1700 includes a display unit1702 configured to display a graphic user interface, optionally, a touchsensitive surface unit 1704 configured to receive contacts, and aprocessing unit 1706 coupled to the display unit 1702 and, optionally,the touch-sensitive surface unit 1704. In some embodiments, theprocessing unit 1706 includes a detecting unit 1708, a transmitting unit1710, a display enabling unit 1712, a causing unit 1714, and a sendingunit 1716. The electronic device 1700, optionally, has a user-interfacelocked state and a user-interface unlocked state and may be in theuser-interface unlocked state.

The processing unit 1706 is configured to detect (e.g., with thedetecting unit 1708), via wireless communication, an external device,wherein the external device has a user-interface locked state and auser-interface unlocked state, and is in the user-interface lockedstate; and transmit (e.g., with the transmitting unit 1710), to theexternal device, unlocking data, where the external device unlocks afterthe external device receives the unlocking information and detects userinput.

In some embodiments, the processing unit 1706 is further configured toenable display (e.g., with display enabling unit 1712) of a visualindication on the electronic device indicating that the external deviceis in the user-interface unlocked state, after the external deviceunlocks.

In some embodiments, the processing unit 1706 is further configured tocause (e.g., with the causing unit 1714) a haptic event on theelectronic device indicating that the external device is in theuser-interface unlocked state, after the external device unlocks.

In some embodiments, the external device displays a visual indicationindicating that the external device is in the user-interface unlockedstate, after the external device unlocks.

In some embodiments, the detected user input is a reading from abiometric sensor of the external device and/or a biometric sensor of theelectronic device.

In some embodiments, the detected user input is a touch on atouch-sensitive input of the external device.

In some embodiments, the detected user input is movement of a mousecoupled to the external device and/or a mouse coupled to the electronicdevice.

In some embodiments, the detected user input is a keystroke on akeyboard of the external device.

In some embodiments, the detected user input is an input on the externaldevice.

In some embodiments, the processing unit 1706 is executing a firstapplication, the processing unit 1706 further configured to send (e.g.,with the sending unit 1716), to the external device, usage informationindicating usage of the first application on the electronic device,where the usage information at least in part causes the external deviceto display an affordance for unlocking and launching a secondapplication on the external device, and where the second applicationcorresponds to the first application.

In some embodiments, the usage information indicates a state of thefirst application, and wherein the state is invoked in the secondapplication when the second application is launched on the externaldevice.

In some embodiments, the electronic device is associated with an e-mailaddress, and the external device unlocks after confirming that theexternal device is associated with the same e-mail address as the e-mailaddress associated with the electronic device.

In some embodiments, an association of the electronic device and theexternal device is stored on an authentication server, and the externaldevice unlocks after confirming, with the authentication server, theassociation.

In some embodiments, the electronic device is associated with a securitydomain, and the external device unlocks after confirming the externaldevice is associated with the same security domain as the securitydomain associated with the electronic device.

In some embodiments, the processing unit 1706 is further configured todetect (e.g., with the detecting unit 1708), via a peer-to-peer wirelesscommunication, the external device.

In some embodiments, the wireless communication comprises Bluetoothcommunication.

In some embodiments, the electronic device is a wearable electronicdevice.

The operations described above with reference to FIG. 13 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.17. For example, detecting operation 1302, transmitting operation 1304,and receiving operation 1306 are, optionally, implemented by eventsorter 170, event recognizer 180, and event handler 190. Event monitor171 in event sorter 170 detects a contact on touch-sensitive display112, and event dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 18 shows a functional blockdiagram of an electronic device 1800 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 18 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 18, an electronic device 1800 includes a display unit1802 configured to display a graphic user interface, optionally, a touchsensitive surface unit 1804 configured to receive contacts, and aprocessing unit 1806 coupled to the display unit 1802 and, optionally,the touch-sensitive surface unit 1804. In some embodiments, theprocessing unit 1806 includes a receiving unit 1808, an unlocking unit1810, a display enabling unit 1812, a prompt enabling unit 1814, alocking unit 1816, a detecting unit 1818, and a causing unit 1820. Theelectronic device 1800, optionally, has a user-interface locked stateand a user-interface unlocked state and may be within wirelesscommunication range of an external device.

The processing unit 1806 is configured to receive (e.g., with thereceiving unit 1808), while in the user-interface locked state, userinput representing a credential for unlocking the electronic device; inresponse to a determination that the credential is valid, unlock (e.g.,with the unlocking unit 1810) the electronic device; after unlocking,enable display (e.g., with the display enabling unit 1812) of, on thedisplay unit of the electronic device, an identification of the externaldevice; and enable prompting (e.g., with the prompt enabling unit 1814)of a user to designate whether the external device is authorized tounlock the electronic device if, in the future, the external devicecomes within wireless communication range of the electronic device whilethe electronic device is in the user-interface locked state.

In some embodiments, the external device causes the electronic device tounlock if the external device is in the user-interface unlocked statewhen the external device comes within wireless communication with theelectronic device.

In some embodiments, the user input is a first user input, theprocessing unit 1806 further configured to lock (e.g., with the lockingunit 1816) the electronic device; detect (e.g., with the detecting unit1818) second user input at the electronic device while the electronicdevice is in the user-interface locked state and the external device iswithin communications range; and in response to detecting the seconduser input, unlock (e.g., with the unlocking unit 1810) the electronicdevice.

In some embodiments, the processing unit 1806 is further configured toenable display (e.g., with the display enabling unit 1812) of a visualindication on the electronic device indicating that the electronicdevice is in the user-interface unlocked state, after the electronicdevice unlocks.

In some embodiments, the processing unit 1806 is further configured toenable display (e.g., with the display enabling unit 1812) of a visualindication on the external device indicating that the electronic deviceis in the user-interface unlocked state, after the electronic deviceunlocks.

In some embodiments, the processing unit 1806 is further configured tocause (e.g., with the causing unit 1820) a haptic event on the externaldevice indicating that the electronic device is in the user-interfaceunlocked state, after the electronic device unlocks.

In some embodiments, receiving user input representing a credential forunlocking the electronic device comprises obtaining a reading from abiometric sensor of the electronic device.

In some embodiments, receiving user input representing a credential forunlocking the electronic device comprises detecting a touch on atouch-sensitive input of the electronic device.

In some embodiments, receiving user input representing a credential forunlocking the electronic device comprises detecting mouse movement of amouse coupled to the electronic device.

In some embodiments, receiving user input representing a credential forunlocking the electronic device comprises detecting a keystroke on akeyboard of the electronic device.

In some embodiments, the processing unit 1806 is further configured todetect (e.g., with the detecting unit 1818), via a peer-to-peer wirelesscommunication, the external device.

In some embodiments, the wireless communication comprises Bluetoothcommunication.

In some embodiments, the external device is a wearable electronicdevice.

The operations described above with reference to FIG. 14 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.18. For example, one or more operations described with reference to FIG.14, including detecting operation 1402, determining operation 1404,receiving operation 1406, and displaying operations 1408 and 1410 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying figures, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe appended claims.

1. (canceled)
 2. A method comprising: at an electronic device: while theelectronic device is in a user-interface unlocked state, detecting arequest at an external device to unlock the external device; and inresponse to detecting the request to unlock the external device:providing, from the electronic device, authorization to unlock theexternal device; and providing an output at the electronic device thatindicates that authorization to unlock the external device was providedby the electronic device.
 3. The method of claim 2, wherein the outputincludes a visual output.
 4. The method of claim 3, wherein the visualoutput occupies more than 50% of the display of the electronic device.5. The method of claim 3, wherein the visual output includes a textualindication that the external device has been transitioned in theuser-interface unlocked state.
 6. The method of claim 2, wherein theoutput includes a non-visual output.
 7. The method of claim 6, whereinthe non-visual output includes a haptic output.
 8. The method of claim2, wherein the request to unlock the external device includes a touchinput.
 9. The method of claim 2, wherein the request to unlock theexternal device includes a button press.
 10. The method of claim 2,wherein the request to unlock the external device includes biometricinput received at the external device.
 11. The method of claim 10,wherein the electronic device is unlocked based on the biometric inputand a proximity of the external device to the electronic device.
 12. Anelectronic device, comprising: one or more processors; memory; and oneor more programs, wherein the one or more programs are stored in thememory and configured to be executed by the one or more processors, theone or more programs including instructions for: while the electronicdevice is in a user-interface unlocked state, detecting a request at anexternal device to unlock the external device; and in response todetecting the request to unlock the external device: providing, from theelectronic device, authorization to unlock the external device; andproviding an output at the electronic device that indicates thatauthorization to unlock the external device was provided by theelectronic device.
 13. A non-transitory computer-readable medium storingone or more programs configured to be executed by an electronic devicewith one or more processors, the one or more programs includinginstructions for: while the electronic device is in a user-interfaceunlocked state, detecting a request at an external device to unlock theexternal device; and in response to detecting the request to unlock theexternal device: providing, from the electronic device, authorization tounlock the external device; and providing an output at the electronicdevice that indicates that authorization to unlock the external devicewas provided by the electronic device.